Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds Allowly Hiring Evidence to the Tools table.
The service runs structured employment-screening fields through an approved deterministic policy, records linked reviews and corrections, and exports Hiring Decision Packs with signed records. That makes it relevant to the list's policy-as-code and evidence-automation themes.
I am the founder of Allowly and maintain this product.
The hosted application repository is private. Its product documentation, API contract, Screening Decisions Profile, and verifier documentation are public. The self-serve core plan is free, with a shared limit of one active item and 1,000 lifetime decisions.
The entry deliberately does not claim that the records prove fairness, source truth, reviewer identity, downstream enforcement, completeness, bias auditing, or legal compliance.
AI Provenance Declaration
AI tool(s)/model(s) used (if any): OpenAI Codex
Human review performed on AI-generated parts (what/how): No human review was performed before submission. Codex checked the wording against the public product documentation and this repository's contribution rules.
Dependency Changes
sscsb deps check) and approvedMerge Policy Reminder
Merges to protected branches must be signed by an approved human hardware-backed
key. When AI involvement is declared above, the merge commit needs review
evidence (
Reviewed-by:trailer). Seedocs/signing.md.